Contactless card that receives power from host device

ABSTRACT

A memory card compatible RFID card includes a smartcard controller that receives power from a host device. The RFID card also includes a small inductive device capable of inductive coupling with an RFID reader. The small inductive device is small enough to fit in the form factor of a memory card. Commands may be sent to the RFID card to keep the RFID card powered.

RELATED APPLICATIONS

This application is a Continuation of U.S. Nonprovisional applicationSer. No. 13/081,775, by Narendra et al., filed Apr. 7, 2011, which is aDivisional of U.S. Nonprovisional application Ser. No. 12/188,346, byNarendra et al., filed Aug. 8, 2008, all of which are incorporatedherein by reference in their entirety for all purposes.

FIELD

The present invention relates generally to contactless communicationsdevices, and more specifically to small radio frequency identification(RFID) cards.

BACKGROUND

RFID “tags” can be separated into two broad categories: active tags andpassive tags. Active tags are characterized by a local power source suchas a battery. Active tags generally transmit information by broadcastingon an RF carrier frequency of choice using a locally generated RFcarrier. Active tags are typically used to transmit over long distances,often referred to as “far field communications” (FFC). Antennas usedwith active RFID tags tend to be large to allow for the communicationsover long distances.

Passive tags are not powered. Passive tags derive the energy needed topower the tag from an interrogating RF field, and use that energy totransmit response codes by modulating the impedance that the antennapresents to the interrogating field, thereby modulating the signalreflected back to the reader antenna. Passive tags are typically used totransmit over short distances, often referred to as “near fieldcommunications” (NFC). For example, passive tags operating at 13.56 MHzare typically designed to communicate with RFID readers a fewcentimeters away.

Passive tags are typically connected to “loop antennas.” One example ofa loop antenna is shown in U.S. Pat. No. 6,568,600, issued to Carpier etal. on May 27, 2003 (the '600 patent). The device described in the '600patent is recognizable as a “credit card sized” passive RFID card (morespecifically, a card that conforms to ISO 7816 size requirements). Theloop antenna is necessarily large because passive tags are powered usingenergy received by the antenna from signals transmitted by the RFIDreader.

FIG. 12 shows a power supply voltage developed over time by rectifying avoltage induced in a loop antenna in the presence of an interrogating RFfield. Once the power supply voltage reaches a critical value, the tagis powered up and can operate. As the antenna size is reduced, it takeslonger for the power supply voltage to reach the critical value, and thetag operation may not meet response time specifications. Below a certainantenna size, the power supply voltage may never reach the criticalvalue, and the tag may never power up.

Antenna design for RFID applications is described in a MicrochipTechnology, Inc. application note entitled “Antenna Circuit Design forRFID Applications” by Youbok Lee, Ph.D., published in 2003 (no monthgiven). Dr. Lee's application note describes in great detail how todetermine size requirements for a passive RFID tag antenna to operate at13.56 MHz. On page 5 of the application note, Dr. Lee shows that theoptimum radius of the loop antenna coil is equal to 1.414 times therequired read range. This analysis confirms that for a read range on theorder of a few centimeters, a credit card sized loop antenna can be madenear optimal.

Passive tags are seeing widespread use in many applications. Forexample, mobile device manufacturers are embedding passive RFID tags inmobile devices for NFC applications. Example mobile applicationsinclude, but are not limited to, ticketing and mobile payments. U.S.Pat. No. 7,333,062 issued to Leizerovich et al. on Feb. 19, 2008 (the'062 patent) shows a mobile phone with an integrated loop antenna for anNFC device. As shown in the '062 patent, the mobile phone provides thereal estate necessary to implement a loop antenna at 13.56 MHz.

There have been attempts to implement passive tags in smaller mobiledevices. These attempts have met with limited success due in part to thesize of the loop antenna. For example, FIG. 13 shows an RFID tagimplementation in a secure digital (SD) memory card manufactured byWireless Dynamics, Inc. of Calgary, Alberta Canada. Card 1300 includesan antenna, but the SD card is significantly oversized as a result. Alsofor example, U.S. Patent Application Publication No.: US 2006/0124755 A1shows a memory card having a passive tag, but the card must be insertedinto a slot to access a loop antenna on a different device. In thisimplementation, mobile device real estate is still relied upon for loopantenna implementation. It can be seen, therefore, that the size ofantennas are proving to be a barrier to further miniaturization ofpassive RFID tags.

A need exists for a small footprint RFID tag that does not rely on anexternal device to house an antenna. A need also exists for a memorycard compatible RFID tag that is compatible with standard memory cardslots on mobile devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a mobile computing device and a small RFID card compatiblewith a memory card slot;

FIG. 2 shows a block diagram of a mobile computing device;

FIGS. 3A-3B show block diagrams of memory card compatible RFID cardswith integrated inductive elements;

FIG. 4 shows a photograph of a memory card compatible RFID card with anintegrated inductive element;

FIG. 5 shows a data portion of a memory card write command;

FIG. 6-11 show flowcharts of methods in accordance with variousembodiments of the present invention;

FIG. 12 shows a power supply voltage developed over time by rectifying avoltage induced in a loop antenna in the presence of an interrogating RFfield; and

FIG. 13 shows a prior art RFID tag implementation in a secure digital(SD) memory card.

DESCRIPTION OF EMBODIMENTS

In the following detailed description, reference is made to theaccompanying drawings that show, by way of illustration, variousembodiments of an invention. These embodiments are described insufficient detail to enable those skilled in the art to practice theinvention. It is to be understood that the various embodiments of theinvention, although different, are not necessarily mutually exclusive.For example, a particular feature, structure, or characteristicdescribed in connection with one embodiment may be implemented withinother embodiments without departing from the spirit and scope of theinvention. In addition, it is to be understood that the location orarrangement of individual elements within each disclosed embodiment maybe modified without departing from the spirit and scope of theinvention. The following detailed description is, therefore, not to betaken in a limiting sense, and the scope of the present invention isdefined only by the appended claims, appropriately interpreted, alongwith the full range of equivalents to which the claims are entitled. Inthe drawings, like numerals refer to the same or similar functionalitythroughout the several views.

FIG. 1 shows a mobile computing device and a small RFID card compatiblewith a memory card slot. Mobile computing device 110 is shown as amobile phone in FIG. 1, but this is not a limitation of the presentinvention. For example, mobile computing device 110 may be a personaldigital assistant (PDA), a smartphone, a mobile phone, a handheldcomputer, a desktop computer, or any other device capable of operatingas described herein.

Mobile computing device 110 includes memory card slot 112. Memory cardslot 112 is a slot capable of accepting RFID card 120. For example,memory card slot 112 may have physical dimensions compatible with RFIDcard 120, and may have a communications interface that operates using aprotocol compatible with RFID card 120. In some embodiments of thepresent invention, memory card slot 112 is a memory card slot designedto accept and communicate with memory cards. As used herein, the term“memory card slot” refers to any add-on slot capable of accepting a cardhaving memory accessible by a mobile computing device such as that shownin FIG. 1. For example, a memory card slot may be compatible with anindustry standard communications protocol, or may be compatible with awidely accepted communications protocol that is not necessarily formallydocumented as an industry standard. Examples include slots that arecompatible with the Multimedia Memory Card (MMC) protocol, Memory StickDUO protocol, secure digital (SD) protocol, and Smart Media protocol.The foregoing list is meant to be exemplary, and not exhaustive. Memorycard slot 112 may be compatible with many memory card slot protocolsother than those explicitly listed above without departing from thescope of the invention.

RFID card 120 includes electrical contacts 122 as part of a hostinterface that communicates with memory card slot 112. For example,electrical contacts 122 may provide connectivity compliant with acommunications protocol for memory cards. RFID card 120 includes RFIDfunctionality, and may also include memory accessible by mobilecomputing device 110. For example, in some embodiments, RFID card 120includes a smartcard controller and an inductive element capable ofinteracting with an NFC reader (e.g., an ISO 14443 compliant interface).In other embodiments, RFID card 120 does not include memory accessibleby mobile computing device 110. RFID card 120 may include functionalitybeyond memory and RFID.

In various embodiments of the present invention, the RFID functionalityin RFID card 120 is accessed by mobile computing device 110 using memorycard access commands already defined for use in memory card slot 112.Accordingly, the various embodiments of the present invention enable theimplementation of RFID functions beyond memory accesses without definingnew commands. In some embodiments, new commands for the RFID card areembedded inside the data bits subsequent to memory card read/writecommands. RFID card 120 then decides if the incoming data bits are meantfor regular read/write memory functions or for RFID functions. In otherwords, functions in addition to standard memory card functions may beaccessed through commands “hidden” in the data stream that can beexchanged using existing memory card access commands and functions.According to the various embodiments of the invention, both existingmemory card functions and RFID functions may be implemented withoutrequiring changes in how the host protocol is built.

The combination of mobile computing device 110 and RFID card 120 may beused for any purpose. For example, in some embodiments, RFID card 120may interact with a point-of-sale payment device to effect mobilepayments. Also for example, in some embodiments, RFID card 120 may beused in wave-and-pay ticketing in mass transit environments, such asMIFARE.

FIG. 2 shows a block diagram of a mobile computing device. Mobilecomputing device 110 includes antenna 240, radio circuits 230, processor210, memory 220, and memory card slot 112. In some embodiments, mobilecomputing device 110 is a mobile phone, or includes mobile phonefunctionality. For example, antenna 240 and radio circuits 230 may beutilized to communicate with a cellular telephone network. Further, insome embodiments, mobile computing device 110 is a wireless local areanetwork (WLAN) or wireless wide area network (WWAN) device. For example,antenna 240 and radio circuits 230 may be utilized to communicate with awireless access point. In some embodiments, antenna 240 and radiocircuits 230 are omitted, and mobile computing device 110 does notutilize wireless connectivity.

Processor 210 represents a processor capable of communicating with theother blocks shown in mobile computing device 110. For example,processor 210 may be a microprocessor, a digital signal processor (DSP),a microcontroller, or the like. Further, processor 210 may be formedfrom state machines or other sequential logic. In operation, processor210 may read instructions from memory 220 and perform actions inresponse thereto. For example, processor 210 may execute programinstructions that influence communications between mobile computingdevice 110 and a device coupled to memory card slot 112.

Memory card slot 112 is described above with reference to FIG. 1. Memorycard slot 112 includes circuitry compatible with RFID card 120. Mobilecomputing device 110 may communicate with RFID card 120 by using astandard set of memory card access commands. For example, processor 210may use memory card write commands to write to memory in RFID card 120,and may use memory card read commands to read from memory in RFID card120.

Mobile computing device 110 may access the RFID functionality in RFIDcard 120 using “hidden” commands embedded in memory card accesscommands. For example, a memory card write command may include a uniquedata string to identify the memory card write command as a command to bediverted for purposes other than a memory write. In addition, the sectoraddress provided with the memory card write command may be set to aparticular address value to further identify the memory card writecommand as a command to be diverted. In addition to specificaddress/data values to identify the memory card access command as acommand to be diverted for a purpose other than a memory access, thememory access command may include data bits to further specify the typeand function of hidden command. Example formats of hidden commands aredescribed further below. In some embodiments, a read command is issuedright after a write command to enable data flow from the non-memory cardfunctions to the host, where the write command's data had the hiddencommands. The combination of a memory card write command and a memorycard read command can be used in this manner to form a hidden readcommand.

In some embodiments, memory card slot 112 is powered down after periodsof inactivity to save power. For example, memory card slot 112 may bepowered up when processor 210 issues a memory card write or readcommand, but may then be powered down to save power. When memory cardslot 112 is powered down, any device coupled to the memory card slot isalso powered down. For example, if RFID card 120 (FIG. 1) is coupled tothe memory card slot, then RFID card 120 is powered down when memorycard slot 112 is powered down.

In various embodiments of the present invention, processor 210 executessoftware resident in memory 220 to maintain power to memory card slot112 (and to RFID card 120). For example, periodic hidden commands may besent to RFID card 120 for the purpose of keeping power applied whileRFID card 120 is expected to be providing RFID functionality. Also forexample, a hidden command may be sent to RFID card 120 for the purposeof cycling power to a smartcard controller resident on the card. Thesehidden commands are described further below with respect to laterfigures.

FIG. 3A shows a block diagram of a memory card compatible RFID card withan integrated inductive element. RFID card 300 represents possibleembodiments of RFID card 120 (FIG. 1). RFID card 300 includes hostinterface 310, memory card controller 340, memory 360, smartcardcontroller 340, program memory 332, and small inductive element 350.RFID card 300 is capable of communicating with a memory card slot in amobile computing device. Further, RFID card 300 does not require memorycard slots to implement extended input/output functions. For example,and not by way of limitation, in SD embodiments, RFID card 300 isoperable in any SD memory card slot, and does not require a securedigital input output (SDIO) memory card slot.

Host interface 310 includes electrical contacts to interface with amemory card slot. For example, host interface 310 includes contacts suchas contacts 122 (FIG. 1). Also for example, in some embodiments, hostinterface 310 includes recessed electrical contacts. Host interface 310may also include circuitry such as drivers, receivers, terminations, andthe like.

In embodiments represented by FIG. 3A, memory card controller 340communicates with the mobile device using memory card access commands.Memory card controller 340 also communicates with memory 360. Memorycard controller 340 determines whether each command should result in amemory operation with memory 360, whether a hidden command should bediverted to smartcard controller 330, or whether memory card controller340 should take action in response to a hidden command. In someembodiments, memory card controller 340 executes instructions that arestored in an internal memory or stored in memory 360. In someembodiments, memory card controller 340 includes special purposehardware useful to determine whether a command should be diverted. Inother embodiments, memory card controller 340 may be a microcontrolleridentical in all respects to a controller found in memory cards, exceptfor the program that it executes.

Memory 360 may be any type of volatile or non-volatile memory. Forexample, memory 360 may be volatile memory such as static random accessmemory (SRAM) or dynamic random access memory (DRAM). Also for example,memory 360 may be nonvolatile memory such as NOR FLASH memory or NANDFLASH memory. In various embodiments of the present invention, memory360 represents memory that is accessed by a mobile computing deviceusing memory card access commands defined for that purpose.

When RFID card 300 is communicating with a memory card slot in a mobilecomputing device, the mobile computing device may send a memory cardaccess command in order to access memory 360. Also for example, themobile computing device may send a memory card access command thatcontains a hidden command. Memory card controller 340 detects thepresence of the hidden command, and diverts all or a portion of thememory access command to smartcard controller 330 using communicationbus 342. Communication bus 342 may have any number of conductors and maytake any form. For example, communication bus 342 may be a serial port,a parallel port, or may include multiple data conductors, multipleaddress conductors, and/or conductors to carry control signals such asclock signals. In some embodiments, memory card controller 340 takes oneor more actions in response to a hidden command. For example, memorycard controller 340 may modify clock signals in response to a hiddencommand.

Memory card controller 340 can detect the hidden command in many ways.For example, in some embodiments, the memory card access command mayinclude a specific address value or a specific data value. Memory cardcontroller 340 detects commands that include one or both of the specificaddress value or specific data value and routes the commandappropriately. The specific address value and specific data value usedfor this purpose are referred to herein as the hidden command addressvalue and the hidden command data value.

In some embodiments, memory card controller 340 detects the presence ofhidden commands based only on the hidden command address value. In theseembodiments, memory card controller 340 checks the address valueincluded in a memory card access command, and diverts the command (ortakes some other action) if it matches the hidden command address value.In some embodiments, memory card controller 340 detects the presence ofhidden commands based only on the hidden command data value. In theseembodiments, memory card controller 340 checks a data value included inthe memory card access command, and diverts the command if it matchesthe hidden command data value. In still further embodiments, memory cardcontroller 340 detects the presence of hidden commands based on both thehidden command address value and the hidden command data value. In theseembodiments, memory card controller 340 diverts the command only if boththe memory card access address and data match the hidden command addressvalue and data value, respectively.

The hidden command address value and hidden command data value may bespecified in many ways. For example, all RFID cards may be issued withfixed values. In these embodiments, each time the RFID functions areaccessed, the same hidden command address and/or data value is includedin the memory card access command. Also for example, different RFIDcards may be issued with unique values. In these embodiments, each RFIDcard may provide these values to a mobile computing device when queried.Also for example, hidden command address and/or data values may bespecified by the mobile computing device. In still further embodiments,hidden command address and data values may be dynamic. The hiddencommand address and data values may change each time power is applied oron a periodic basis.

Smartcard controller 330 receives hidden commands diverted by memorycard controller 340. Smartcard controller 330 further interprets thehidden commands and performs actions in response thereto. Smartcardcontroller 330 executes instructions stored in program memory 332. Insome embodiments, program memory 332 is embedded in smartcard controller330, and in other embodiments, program memory 332 is part of memory 360.

Smartcard controller 330 is a dual interface smartcard controller withone of the interfaces including RFID functionality. In some embodiments,smartcard controller 330 is compatible with passive RFID tag readers inNFC applications. For example, smartcard controller 330 may be a devicecapable of implementing all or part of the ISO 14443 standard forcontactless NFC devices. Also for example, smartcard controller 330 maybe a dual interface smartcard controller capable of implementing bothISO 7816 and ISO 14443 standards for contact/contactless requirements.The “SmartMX” family of controllers available from NXP of TheNetherlands are examples of suitable dual interface smartcardcontrollers. These controllers provide RFID functionality at 13.56 MHz.The various embodiments of the present invention operate at 13.56 MHz,but are not limited to operation at this frequency. In some embodiments,smartcard controller interoperates with MIFARE systems for ticketingapplications.

Smartcard controller 330 receives power from the host interface. By notreceiving power from the interrogating RF field, the necessity of a loopantenna for power generation is negated. Smartcard controller 330includes antenna port 334. Antenna port 334 is coupled to smallinductive element 350.

Small inductive element 350 includes a coil wound around a magneticcore. The coil is too small to draw power from the interrogating RFfield, but this is not necessary since smartcard controller 330 ispowered by the host device through host interface 310. Small inductiveelement 350 interacts with an antenna in an RFID reader similar to theway that primary and secondary coils in a transformer interact. The RFIDreader has a coil resonant at 13.56 MHz functioning as the primary coilof a transformer. Small inductive element 350 functions as the secondarycoil of the transformer. Accordingly, the transmitter “sees” theimpedance of the secondary coil (small inductive element 350). Smartcardcontroller 334 is able to modulate reflected RF signals using circuitryto modify the impedance at the antenna port 334.

Small inductive element 350 can be made very small. For example, in someembodiments, RFID card 120 is a miniSD card, and small inductive element350 is small enough to be completely contained in the miniSD formfactor. A specific embodiment of a small inductive element in a memorycard form factor is described below with reference to FIG. 4.

In various embodiments of the invention, memory card controller 340 andsmartcard controller 330 are implemented in many different ways. Forexample, in some embodiments, the various components are implemented inhardware. In these embodiments, the various components may beimplemented as separate integrated circuits, or in a combined integratedcircuit. Also for example, in some embodiments, the various componentsmay be implemented in software, or in a combination of hardware andsoftware. In some embodiments, RFID card 300 may include amicroprocessor, and the components may be implemented as softwaremodules running on the microprocessor. In other embodiments, RFID card300 may include multiple processors, and the components may beimplemented as software modules distributed across the multipleprocessors.

FIG. 3B shows a block diagram of a memory card compatible RFID card withan integrated inductive element. RFID card 302 represents possibleembodiments of RFID card 120 (FIG. 1). RFID card 302 includes hostinterface 310, memory card controller 340, memory 360, smartcardcontroller 340, program memory 332, and small inductive element 350, allof which are described above with reference to FIG. 3A. RFID card 302 iscapable of communicating with a memory card slot in a mobile computingdevice. Further, RFID card 302 does not require memory card slots toimplement extended input/output functions. For example, and not by wayof limitation, in SD embodiments, RFID card 302 is operable in any SDmemory card slot, and does not require a secure digital input output(SDIO) memory card slot.

In embodiments represented by FIG. 3B, smartcard controller 330 receivespower from memory controller 340. In these embodiments, memorycontroller 340 has direct control over the power provided to smartcardcontroller 330. Memory controller 340 may apply and/or remove power fromsmartcard controller 330 in response to commands received over the hostinterface. For example, memory controller 340 may receive a hiddencommand to reset smartcard controller 330 by causing a reboot through apower cycle.

FIG. 4 shows a photograph of a memory card compatible RFID card with anintegrated inductive element. RFID card 120 is shown in an SD card formfactor, although this is not a limitation of the present invention. RFIDcard 120 includes electrical contacts 122, memory card controller 340,smartcard controller 330, memory 360, magnetic core 450, and coil 452,all affixed to circuit board 402.

Magnetic core 450 and coil 452 implement small inductive element 350(FIG. 3). As can be seen in the photograph, the small inductive elementfits entirely within the memory card form factor. The small inductiveelement does not provide power generation for smartcard controller 330,and so does not need to be made large for that purpose.

FIG. 5 shows a data portion of a memory card write command. Included arehidden command data value 510, status field 520, password field 530,device ID 532, command index 540, and hidden command related data 550.In the example of FIG. 5, the data portion is 512 bytes in length,although this is not a limitation of the present invention. Any amountof data may be included in the write command, and each field shown inFIG. 5 may be any length.

In the example of FIG. 5, the hidden command data value is 256 bitslong, although any length may be used without departing from the scopeof the present invention. In some embodiments, hidden command data value510 is used to identify a memory write command as a hidden command. Whena write command is received having data in the first 256 bits that matchthe hidden command data value, the command is identified as one to bediverted to the smartcard controller. As described above, a hiddencommand address value may be used in conjunction with, or instead of, ahidden command data value to identify the memory write command as ahidden command.

The remaining fields have significance when the memory write is a hiddencommand. For example, if the first 256 bits do not match the hiddencommand data value (or if the write address does not match the hiddencommand address value, or both) then the remaining bits in the datafield are to be treated as data in a normal memory write command. Incontrast, when the memory write is a hidden command, the remainingfields are used to further interpret the hidden command.

Memory card controller 340 (FIGS. 3, 4) inspect the hidden command datavalue 510, status field 520, and possibly password field 530 and deviceID 532. In some embodiments, if the command is identified as a hiddencommand, memory card controller 340 forwards the password 530, commandindex 540, and related data 550 to smartcard controller 330. In otherembodiments, memory card controller 340 may directly take actions basedon the hidden command.

Status field 520 may include any information relating to the status ofthe hidden command. For example, status field 520 may include one morebits to signify to memory card controller 340 whether the host (mobilecomputing device) is expecting the smartcard controller to return datain response to the hidden command. For example, when status field 520signifies a write, memory card controller 340 forwards the passworddevice ID, command index, and related data without expecting to returnany data to the host. Also for example, when status field 520 signifiesa read, memory card controller 340 forwards the password, device ID,command index, and related data with the expectation that smartcardcontroller 330 will provide data to be sent to the host in response to amemory card read command. The combination of a memory card write commandfollowed shortly thereafter by a memory card read command may be used toprovide “read” functionality to the smartcard controller. Readoperations from the smartcard controller are described further belowwith reference to FIG. 8.

Password field 530 includes a password to allow smartcard controller 330to authenticate the host to the token. In some embodiments, every hiddencommand includes a password. Each time the password, device ID, commandindex, and related data is diverted to the smartcard controller, thepassword is checked to authenticate the host to the token.

Device ID 532 uniquely identifies the host (mobile computing device).The device ID may be checked by the smartcard controller to ensure thatthe token is inserted in the host to which it is authenticated. Someembodiments of the present invention enforce a unique host/card pairingusing the device ID, and other embodiments allow smartcard controllerfunctions to be accessed by any host.

Command index 540 identifies the type of hidden command. The number ofpossible hidden commands is limited only by the number of bits allocatedthereto. Any number of bits may be allocated to command index 540without departing from the scope of the present invention. Hiddencommand related data 550 may be utilized differently for each type ofhidden command. Any number of bits may be used for hidden commandrelated data 550.

The data shown in FIG. 5 is provided as an example, and the data fieldof a memory card access command may include more or fewer data fieldsthan those shown in FIG. 5. The present invention is not limited by thenumber or content of the fields in a memory card access command.

FIG. 6 shows a flowchart in accordance with various embodiments of thepresent invention. In some embodiments, method 600 may be used by amobile computing device to communicate with an RFID card in a memorycard slot. In some embodiments, method 600, or portions thereof, isperformed by a mobile computing device with a memory card slot, and inother embodiments, method 600, or portions thereof, is performed bysoftware. The various actions in method 600 may be performed in theorder presented, in a different order, or simultaneously. Further, insome embodiments, some actions listed in FIG. 6 are omitted from method600.

Method 600 begins at 610 in which a data pattern and an address valueare received from an RFID card in a memory card slot. The data patterncorresponds to the hidden command data value, and the address valuecorresponds to the hidden command address value. In some embodiments,the mobile device only receives the data value and in other embodiments,the mobile device only receives the address value. In some embodiments,the actions of 610 may occur once when the RFID card is first insertedin the memory card slot. The mobile computing device may then use theaddress and data values each time it creates a hidden command. In otherembodiments, the actions of 610 may occur each time the RFID card isinserted in the memory slot. In still further embodiments, the actionsof 610 may occur periodically. Each time the actions 610 occur, the datapattern may be the same or different, and the address value may be thesame or different.

At 620, a data field of a memory card access command is populated withthe data pattern to cause the command to be diverted to a smartcardcontroller on the RFID card. For example, the data pattern may bewritten to the data field as the hidden command data value 510 (FIG. 5).

At 630, an address field of the memory card access command is populatedwith the address value to further cause the command to be diverted tothe smartcard controller. In some embodiments, only one of 620 or 630 isutilized. In these embodiments, the presence of a hidden command issignified by the data pattern alone, or the address value alone.

At 640, the data field of the memory card access command is populatedwith a command string to specify a purpose other than a memory cardaccess. For example, the command string may be written to the data fieldas the command index 540 for the smart card controller. This command maybe used for any purpose. For example, one or more hidden commands mayhave as a sole purpose keeping power provided to the memory card slot sothat the RFID card continues to receive power.

At 650, the data field of a memory card access command is populated witha password to authenticate access to the RFID card coupled to the memorycard slot. In some embodiments, a password is included in the data fieldfor every hidden command. In other embodiments, a password is onlyincluded at the beginning of an exchange.

At 660, the memory card access command is sent to the RFID card coupledto the memory card slot. For example, a mobile computing device (110,FIGS. 1, 2) may send the memory card access command to an RFID card(120, FIGS. 1, 3, 4) in a memory card slot (112, FIGS. 1, 2). The RFIDcard includes a memory card controller (340, FIG. 3) to divert thecommand (or take some other action) based on the data fields populatedin method 600.

FIG. 7 shows a flowchart in accordance with various embodiments of thepresent invention. In some embodiments, method 700 may be used by anRFID card in a memory card slot. In some embodiments, method 700, orportions thereof, is performed by a memory card controller within amemory card compatible RFID card, and in other embodiments, method 700,or portions thereof, is performed by software. The various actions inmethod 700 may be performed in the order presented, in a differentorder, or simultaneously. Further, in some embodiments, some actionslisted in FIG. 7 are omitted from method 700.

Method 700 begins at 710 in which a memory card access command isreceived from a mobile computing device via a host interface. Theactions of 710 correspond to an RFID card in a memory card slot of amobile computing device receiving a memory card access command.

At 720, the memory card controller checks criteria in the memory cardaccess command to determine if the memory card access command should bediverted to a smartcard controller resident on the RFID card. Thecriteria may be one or both of a hidden command data value, a hiddencommand address value, or both. If there is a criteria match at 730,then a hidden command is present, and at least a portion of the memorycard access command is diverted at 740. If there is not a criteriamatch, then no hidden command is present, and a memory access isperformed at 750.

FIG. 8 shows a flowchart in accordance with various embodiments of thepresent invention. In some embodiments, method 800 may be used by anRFID card in a memory card slot. In some embodiments, method 800, orportions thereof, is performed by a memory card controller within anRFID card, and in other embodiments, method 800, or portions thereof, isperformed by software. The various actions in method 800 may beperformed in the order presented, in a different order, orsimultaneously. Further, in some embodiments, some actions listed inFIG. 8 are omitted from method 800.

Method 800 begins at 810 in which a memory card write command isreceived from a mobile computing device via a host interface. If thememory card write command is determined to be a hidden command,processing continues with 840; otherwise, a memory write is performed at830.

At 840, the hidden command is diverted to a smartcard controller. If thehidden command is determined to be a “read” at 850, processing continuesat 860; otherwise, the hidden command processing is done. At 860, thememory card controller retrieves non-memory data from the smartcardcontroller, and at 870, a memory card read command is received from themobile computing device. At 880, the non-memory data is returned to themobile computing device.

Method 800 demonstrates how a mobile computing device can perform a readfrom a smartcard controller in a memory card compatible RFID card. Themobile computing device issues a memory card write command with a hiddencommand having a status field designating a read, and then the mobilecomputing device issues a memory card read command. The processing inthe card receives the hidden command, identifies it as a read, and thenreturns data to the mobile computing device in response to a subsequentmemory card read command.

FIG. 9 shows a flowchart in accordance with various embodiments of thepresent invention. In some embodiments, method 900 may be used by anRFID card in a memory card slot. In some embodiments, method 900, orportions thereof, is performed by a smartcard controller within an RFIDcard, and in other embodiments, method 900, or portions thereof, isperformed by software. The various actions in method 900 may beperformed in the order presented, in a different order, orsimultaneously. Further, in some embodiments, some actions listed inFIG. 9 are omitted from method 900.

Method 900 begins at 910 in which a smartcard controller receives acommand from the memory card controller. This command corresponds to ahidden command received by the memory card controller. At 950, thesmartcard controller determines whether the command is a “dummy” commandused solely for the purpose of maintaining power to the memory cardslot. If no, then the smartcard function specified in the command isperformed at 930. If yes, then the command is disregarded at 960.

Method 900 allows a memory card compatible RFID card in a memory cardslot to remain powered during periods when the memory card slot in thehost device would otherwise remove power to save energy. This is acoordinated effort between software building hidden commands in a memorycard access command, the memory card controller diverting the hiddencommand to the smartcard controller, and the smartcard controllerdisregarding the command. According to embodiments represented by FIG.3A, providing power to the RFID card also provides power the smartcardcontroller, thereby allowing the use of a small inductive device such asthose shown in FIGS. 3 and 4.

FIG. 10 shows a flowchart in accordance with various embodiments of thepresent invention. In some embodiments, method 1000 may be used by anRFID card in a memory card slot. In some embodiments, method 1000, orportions thereof, is performed by a memory card controller within anRFID card, and in other embodiments, method 1000, or portions thereof,is performed by software. The various actions in method 1000 may beperformed in the order presented, in a different order, orsimultaneously. Further, in some embodiments, some actions listed inFIG. 10 are omitted from method 1000.

Method 1000 begins at 1010 in which a memory card controller receives ahidden command from a mobile computing device. If at 1020, the memorycard controller determines that the hidden command is to be diverted tothe smartcard controller, then the command is diverted at 1030. If thecommand is not to be diverted, then the memory card controller does notdivert the command; however, the memory card controller may take otheractions at 1040 based on the hidden command. For example, the memorycard controller may modify a clock signal provided to the smartcardcontroller. Also for example, the memory card controller may assert areset signal to the smartcard controller. Still for example, the memorycard controller may cycle power to the smartcard controller. The memorycard controller is able to cycle power to the smartcard controller inembodiments represented by FIG. 3B.

Cycling power to the smartcard controller may be a coordinated effortbetween the hosting computing device and the memory card controller inthe RFID card. For example, power to the memory card slot may bemaintained by supplying dummy hidden commands to the RFID card asdescribed above with reference to FIG. 9. While power is maintained tothe memory card slot, hidden commands may be used to cause the memorycard controller to cycle power to the smartcard controller.

FIG. 11 shows a method authenticating a mobile computing device to oneor more functions in a memory card compatible RFID card. Method 1100begins at block 1110 in which an activation code is received at an RFIDcard from a mobile computing device. At 1120, the received activationcode is compared to a code stored in the RFID card. If the activationcode matches, the RFID card receives a password from the mobilecomputing device at 1140, and stores the password in the RFID card forlater use at 1150. If the activation code does not match, the RFID carddetermines whether a number of allowable tries has been exceeded at1160. If the number of allowable tries has been exceeded, the RFID cardissuer is contacted at 1170, and if the number of allowable tries hasnot been exceeded, the method repeats until either the activation codematches or the number of allowable tries has been exceeded.

Method 1100 may be performed when an RFID card is issued to a user. Forexample, the RFID card may be a mobile payment card issued by afinancial institution. The user may be provided an activation code to“activate” the RFID card. When the user successfully enters theactivation code, the user is prompted for a password, and that passwordis stored for use in future hidden commands.

In some embodiments, multiple non-memory functions in an RFID card areauthenticated using method 1100. For example, each of multiplenon-memory functions may have stored activation codes, and each isactivated separately. Each of the separately activated functions mayhave a different password, or the multiple functions may share apassword.

Although the present invention has been described in conjunction withcertain embodiments, it is to be understood that modifications andvariations may be resorted to without departing from the spirit andscope of the invention as those skilled in the art readily understand.Such modifications and variations are considered to be within the scopeof the invention and the appended claims.

What is claimed is:
 1. A card comprising: a memory card slot interface;a memory card controller coupled to the memory card slot interface; acontactless communications device coupled to the memory card controller,the contactless communications device having an antenna port; a powerdelivery mechanism to deliver power to the contactless communicationsdevice from the memory card slot interface; and a coil coupled to theantenna port of the contactless communications device.
 2. The card ofclaim 1 wherein the contactless communications device is designed tocomply with ISO
 14443. 3. The card of claim 1 wherein the contactlesscommunications device is designed to interoperate with MIFARE.
 4. Thecard of claim 1 wherein the card conforms to memory card sizerequirements of a micro SD card.
 5. The card of claim 1 furthercomprising a circuit board to which the memory card controller, thecontactless communications device, and the magnetic core and coil areaffixed.
 6. The card of claim 1 wherein the contactless communicationsdevice is operable to reflect signals received at substantially 13.56MHz.
 7. The card of claim 1 further comprising nonvolatile memorycoupled to the memory card controller.
 8. A memory card comprising: amemory card controller to communicate with a host; a smartcardcontroller having an antenna port; and an inductive element coupled tothe antenna port, wherein the inductive element is too small to providesufficient energy to power the smartcard controller; wherein thesmartcard controller is coupled to receive power from the host.
 9. Thememory card of claim 8 wherein the smartcard controller is designed tocomply with ISO
 14443. 10. The memory card of claim 8 wherein thesmartcard controller is designed to interoperate with MIFARE.
 11. Thememory card of claim 8 wherein the card conforms to memory card sizerequirements of a micro SD card.
 12. The memory card of claim 8 furthercomprising a circuit board to which the memory card controller, thesmartcard controller, and the inductive element are affixed.
 13. Thememory card of claim 8 wherein the smartcard controller is operable toreflect signals received at substantially 13.56 MHz.
 14. A mobilepayment device comprising: a coil to inductively couple with aninterrogating radio frequency field transmitted by a mobile paymentreader; a dual interface smartcard controller having an antenna portcoupled to the coil, the dual interface smartcard controller furthercoupled to receive power from other than the antenna port; a memory cardcontroller coupled to communicate with the dual interface smartcardcontroller; and a memory card compatible circuit board upon which thecoil, the dual interface smartcard, and the memory card controller aremounted.
 15. The mobile payment device of claim 14 further comprisingmetallic contacts compatible with a memory card slot in a host device.16. The mobile payment device of claim 15 wherein the dual interfacesmartcard controller is coupled to the metallic contacts to receivepower from the host device.
 17. The mobile payment device of claim 14wherein the dual interface smartcard controller is coupled to receivepower from the memory card controller.
 18. The mobile payment device ofclaim 14 wherein the mobile payment device conforms to memory card sizerequirements of a micro SD card.
 19. The mobile payment device of claim18 further comprising nonvolatile memory coupled to the memory cardcontroller.
 20. The mobile payment device of claim 14 wherein the dualinterface smartcard controller is operable to reflect signals receivedat substantially 13.56 MHz.